User interface for screencast applications

ABSTRACT

An electronic device determines that an application has been launched for which screencasting is available. In response, the device displays a screencast control panel. A user inputs an instruction to begin screencasting via the control panel. In response to this instruction, the electronic device screencasts media content including content created by the application. A rate of screencasting is determined by a Frame Rate Conversion (FRC) module.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of application Ser. No. 17/347,410, filed Jun. 14, 2021, entitled “USER INTERFACE FOR SCREENCAST APPLICATIONS,” which is a continuation of application Ser. No. 15/294,261, filed Oct. 14, 2016, now issued as U.S. Pat. No. 11,036,458 on Jun. 15, 2021, entitled “USER INTERFACE FOR SCREENCAST APPLICATIONS,” which claims the benefit of U.S. Provisional Patent Application Nos. 62,241,637, filed Oct. 14, 2015, titled “METHOD FOR AUTOMATICALLY SCREENCASTING APPS ON A MOBILE DEVICE,” and 62/241,634, filed Oct. 14, 2015 titled, “MOBILE SCREENCAST USER INTERFACE,” which are incorporated by reference herein.

BACKGROUND FIELD

This disclosure relates generally to capturing and streaming of media content, and in particular to capturing video and audio content associated with game play directly from a mobile device.

Description of Related Art

One popular type of content on video hosting sites is videos depicting gameplay captured on video game consoles or desktop computers. Technology exists on those platforms to capture and record the screen contents and the system audio. Additionally, video and audio recordings of the game player are sometimes obtained via a webcam and microphone and presented in conjunction with the gameplay content.

As game play moves to mobile devices, gaming video creators will need a way to capture gameplay on those devices. Today, this is typically accomplished by connecting a mobile device to specialized recording equipment, which is generally suitable only for professionals. Furthermore, current approaches require privileged access to certain system resources or require modification of the applications in order to record.

SUMMARY

Disclosed embodiments include user interfaces for controlling screencasting from an electronic device (e.g., a mobile device). In some embodiments of the computer-implemented method, a screencast control panel is displayed in response to detecting that an application has been launched. An instruction to begin screencasting is received via user input using the screencast control panel. Media content including content generated by the application is then screencast in response to the instruction. The rate of screencasting is determined by a frame rate conversion (FRC) module. Some embodiments of the non-transitory computer-readable medium include instructions that, when executed, cause one or more processors to perform the computer-implemented method. Some embodiments of the electronic device includes such a non-transitory computer-readable medium and one or more processors for executing the instructions.

The features and advantages described in this summary and the following description are not all inclusive and, in particular, many additional features and advantages will be apparent in view of the drawings, specification, and claims. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the disclosed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed embodiments have other advantages and features that will be more readily apparent from the detailed description and the accompanying figures. A brief introduction of the figures is below.

FIG. 1 is a block diagram of the overall architecture of one embodiment of a stream capture system.

FIG. 2 is a block diagram of a mobile device in accordance with one embodiment.

FIG. 3 is a block diagram illustrating display sandboxing in accordance with one embodiment.

FIG. 4 is a block diagram illustrating operation of a video capture module in accordance with one embodiment.

FIG. 5 is a block diagram illustrating operation of a frame rate conversion module in accordance with one embodiment.

FIG. 6 is a block diagram illustrating operation of a video encoder in accordance with one embodiment.

FIG. 7 is a flow chart of a conceptual buffer scheme for audio sandboxing in accordance with one embodiment.

FIG. 8 is a block diagram illustrating operation of an audio capture module in accordance with one embodiment.

FIG. 9 is a block diagram illustrating operation of an audio encoder in accordance with one embodiment.

FIG. 10 is a block diagram illustrating operation of an A/V multiplexer in accordance with one embodiment.

FIG. 11 is a block diagram illustrating operation of a stream capture system in accordance with one embodiment.

FIG. 12 is a high-level block diagram illustrating an example of a computer for use in a stream capture system according to one embodiment.

FIGS. 13A-G are screenshots illustrating a user interface for launching a screencasting session, according to various embodiments.

FIGS. 14A-K are screenshots illustrating a user interface for operating a screencast session, according to various embodiments.

DETAILED DESCRIPTION

In many instances, the operating system of mobile devices limits access to what is displayed on the screen and output by speakers of a mobile device to certain privileged applications. These applications are generally those provided by the manufacturer of the device and sometimes certain trusted partners (e.g., a telecom company that provides the device to its customers). In various embodiments, a screencasting application with such privileged access is used to enable screencasting of third party applications (e.g., games). Alternatively, the screencasting functionality can be built into applications that are provided by the manufacturer or a trusted partner (“1st party applications”).

In some embodiments, the screencasting application employs sub-composition of graphics layers in recording and streaming videos, which allows capture of only the relevant video layers and not other layers (e.g., user notifications) that are displayed locally. In one such embodiment, each layer is tagged with its owning application and a user can select which layers to pre-compose via a screencast application (e.g., a dedicated screencast application that creates the screencast recording or live stream on behalf of another application). Alternatively, the screencast control functionality can be built into the application (e.g., a game provided by the device manufacturer) that is to be streamed. The sub-composition is made available to the requesting application, and the remaining layers are added to the sub-composition layers for local display. For example, video from a game and video captured by a front- or rear-facing camera might be included in the pre-composition, while system notifications might only be produced locally.

Additionally or alternatively, the screencasting application may employ virtual display frame rate conversion (FRC), which improves encoder logic for better video with less lag. A virtual display represents a display device on which normal graphics can be drawn. In one embodiment, the content of a virtual display includes a copy of the content of the physical display screen. The content of the virtual display can then be mapped to a physical display, e.g., remote projection over an HDMI port, or piped into an encoder to make a video.

In some embodiments, the screencasting application employs sub-mix of audio tracks (also referred to herein as “audio layers”) such that the application only captures the target application's audio and not unrelated system audio. In one such embodiment, each audio track is tagged with its owning application and the user can select which audio tracks to pre-mix. The pre-mix is made available to the requesting application, and the remaining tracks and pre-mix are mixed for local audio output. For example, audio from a game and the device's microphone might be included in the pre-mix, while unrelated audio such as system notifications and music not related to the game is only reproduced locally.

In other embodiments, the screencasting application employs audio stream and track duplication, in which the requesting application can capture audio while it continues to play through the local output (e.g., speakers or headphones). In still other embodiments, the screencasting application employs sub-mix permissions, which allow third party applications to mark audio tracks as secure such that they are not recorded.

In further embodiments, the screencasting application captures the primary display output (e.g., pixel data from the frame buffer) and the primary audio output (e.g., sample data from the speaker).

Regardless of the details of how it is captured, in various embodiments, the screencasting application encodes the captured display output in a video hosting service-compatible video format and encodes the captured audio in a hosting service-compatible audio format. The screencasting application then multiplexes the video and audio data into a file container format. The multiplexed video and audio data can be streamed live, saved locally and uploaded to a video content hosting service at a later time, or both.

In various embodiments, the full set of encoder capabilities are made available to requesting applications. This enables the screencast application to select the best codec with the most useful set of parameters for the recording or live stream, based on characteristics such as whether there is hardware acceleration, the best frame rate that can be sustained, the highest bitrate that can be sustained, etc. Foreground application detection enables the screencast application (i.e., the application making the screencast recording or live stream) to be notified when the requesting application (i.e., the application being recorded or streamed) is or is no longer in the foreground, thus allowing screencasting to be paused or resume recording, if desired, so that only the activity of one or more target applications is captured. In some embodiments, the screencast application provides controls to allow the user to enable and disable video and audio capture.

As noted above, the described embodiments enable screencasting from mobile devices to a video content hosting service. In some embodiments, the encoded video is first saved to a video file stored locally on the device, and later uploaded to the video content hosting service. In other embodiments, screencasting occurs substantially in real-time by streaming the encoded video to the video hosting service for live broadcast.

In some embodiments, the screencasting application captures the video preview from a front- or rear-facing camera, encodes the preview in a video hosting service-compatible video format, and includes the preview as a separate video track in the screencast. In one such embodiment, the front-facing camera is overlaid on top of the display, and a single video is delivered to the video hosting service. In another embodiment, the front-facing camera is recorded as its own separate video track or stream, and either visible or not visible to the user on-screen. Two video tracks, screencast and camera, are then composited by the video hosting service into a variety of formats to produce multiple versions of a single video stream, e.g. side-by-side, camera overlaid in top right corner, screencast overlaid on camera, etc.

On many mobile platforms, two barriers often exist that prevent recording the primary audio output for screencasting. First, sound may not be played locally when the output is being recorded. Second, sample data must be copied to the encoder by a separate, application-level process, which introduces added latency. To obviate these difficulties, in one embodiment the audio framework on the mobile device is extended to enable simultaneous delivery of buffers of sample data to the downstream mixer for output, as well as to the encoder. To avoid additional data copies, audio buffers support multiple consumers. Additionally, an interface is provided to applications to request delivery of a “record” mix to an audio encoder, similar to the existing “remote” sub-mix but tagged to a particular application and any additional desired tracks.

With the ability to screencast applications from a mobile device, it becomes desirable to automatically provide screencasting functionality on the launch of certain applications. For example, a user might want to screencast every time they play a particular game. In addition, as the display on mobile devices is generally smaller than that on desktop or laptop computers, an efficient and compact user interface for controlling screencast sessions is desirable.

In various embodiments, a screencast layer is overlaid on top of all other display layers. This screencast layer can include, among other things, controls for managing the screencast (e.g., start, stop, pause, resume, insert ad break, insert slate, audio bleep, etc.), an indicator that the display is currently being screencast, and a self-camera view of the user (e.g., obtained from a front-facing camera of the mobile device). This helps ensure that the user is notified when screencasting in occurring and can easily control the session. In one embodiment, to minimize obstruction of the underlying display, the screencast controls are initially minimized, being represented by a small indicator (e.g., in one corner of the display) and only expanded in response to user input (e.g., by selecting the indicator). In other embodiments, control of the screencast is implemented through gestures (e.g., swipe, double tap, hot zones, etc.) in addition or alternatively to providing controls on the display.

Reference will now be made in detail to several embodiments, examples of which are illustrated in the accompanying figures. It is noted that wherever practicable similar or like reference numbers may be used in the figures and may indicate similar or like functionality. The figures depict embodiments of the disclosed system (and method) for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles described herein.

FIG. 1 illustrates a block diagram of a system 100 for providing stream capture, recording, and streaming of video game content on a mobile device in accordance with one embodiment. In the embodiment shown, the system 100 includes a video hosting service 105, a content provider 130, a mobile device 135, and a client device 170, all connected via a network 140 (e.g., the Internet). Other embodiments of the system 100 include different or additional components. In addition, the functions may be distributed among the components in a different manner than described herein.

In one embodiment, the video hosting service 105 stores and provides videos to clients such as a client device 170 and mobile device 135, including both user-generated videos and commercially/professionally generated videos. The user-generated videos include screencasts of games played on a mobile device 135. The video hosting service 105 communicates with a plurality of content providers 130 and client devices 170 via the network 140 to facilitate sharing of video content between users. Note that although FIG. 1 only shows one content provider 130, mobile device 135, and client device 170 for the sake of clarity, there can be any number of each.

In the embodiment shown in FIG. 1, the video hosting service 105 includes a front end interface 110, a video serving module 115, a video search module 120, an upload server 125, a user database 145, a media repository 150, and a video tracking module 160. Other conventional features, such as firewalls, load balancers, authentication servers, application servers, failover servers, site management tools, and so forth are not shown so as to more clearly illustrate the features of the video hosting service 105. One example of a suitable service 105 is YouTube1M. Other video hosting services are known and can be adapted to operate according to the teachings disclosed herein. Similarly, systems that host audio recordings, images, interactive graphics, text or hypertext documents, and downloadable applications can be adapted to be operated as described herein.

The illustrated components of the video hosting service 105 can be implemented as single or multiple components of software and hardware. In general, functions described in one embodiment as being performed by one component can also be performed by other components in other embodiments, or by a combination of components. Furthermore, functions described in one embodiment as being performed by components of the video hosting service 105 can also be performed by one or more client devices 170 in other embodiments if appropriate.

In one embodiment, the front end interface 110 provides the interface between the client device 170 and the various components of the video hosting service 105. The upload server 125 of the video hosting service 105 receives video content from a content provider 130, and processes the content for storage and playback. The received content is stored in the media repository 150. In response to requests from the client devices 170, a video serving module 115 provides video data from the media repository 150 to the client devices 170. The video search module 120 enables users to search the media repository 150, such as by entering textual queries containing keywords of interest or using playlists, channels, recommendations, and the like.

In some embodiments, the user database 145 is configured to maintain a record of registered users of the video hosting service 105. Registered users include content providers and/or users of the client devices 170 who view videos on the video hosting service 105. Each content provider 130 and/or individual user registers account information, which may include login name, electronic mail (e-mail) address, and password with the video hosting service 105, and is provided with a unique user ID. The user ID can be based on any identifying information, such as the user's IP address, user name, or the like. This account information is stored in the user database 145. Users have the opportunity to specify that the account information not be shared with other components of the video hosting service 105, or with other third-party systems. In some embodiments, users that have not registered may still use the video hosting service 105, though some features may be unavailable to unregistered users.

In various embodiments, the media repository 150 contains a set of media content items 155 submitted by users. The media repository 150 can contain any number of media content items 155, such as tens of thousands or hundreds of millions. Each of the media content items 155 has a unique identifier that distinguishes it from each of the other media content items, such as a textual name (e.g., the string “a91qrx8”), an integer, or any other way of uniquely naming the content item. The media content items 155 can be packaged in various containers such as AVI, MP4, MOV, or WebM, and can be encoded using codecs such as VP8, MPEG-2, MPEG-4, H.264, and the like. In one embodiment where a mobile device 135 is capturing media content such as game play footage and transmitting it to the video hosting service 105 for live streaming, the upload server 125 receives the stream from the mobile device 135, passes it to the media repository 150, and the stream is then made available immediately to the client devices 170. Alternatively, the media content might be streamed live but not recorded, and never sent to the media repository 150.

In some embodiments, the videos 155 have associated metadata 155A in addition to audiovisual content. In one such embodiment, the metadata 155A include textual metadata such as a video title, a video description, and/or tags provided by a user who uploaded the video, as well as user comments provided by users viewing the video. The metadata 155A may also include an uploader-specified category designating one of a set of categories specified by the video hosting service 105, such as games, sports, entertainment, music, or the like. Although such textual metadata are typically provided by the video uploader and/or other users, they may also be provided or modified automatically by the video hosting service 105.

The client devices 170 are computing devices that execute client software, e.g., a web browser or built-in client application, to connect to the front end interface 110 of the video hosting service 105 via a network 140 and display videos. A client device 170 might be, for example, a personal computer, a personal digital assistant, a cellular, mobile, or smart phone, laptop computer, television, set top box, game console, public indoor or outdoor display, movie theater, or wearable computer.

Conceptually, the content provider 130 (and the mobile device 135 when it is providing gaming videos to be streamed live or stored) is an entity that provides video content to the video hosting service 105. In practice, some content providers (e.g., individual users who upload user generated content) may also be content viewers. Additionally, the content provider 130 may be provided by the same entity that operates the video hosting service 105. Content provider functions may include, for example, uploading a video file to the video hosting service 105, editing a video file stored by the video hosting service 105, or editing content provider preferences associated with a video file.

The client device 170 operates on a device to view video content stored by the video hosting service 105. The client device 170 may also be used to configure viewer preferences related to video content. In some embodiments, the client device 170 includes an embedded video player adapted for the video file formats used in the video hosting service 105. Note that the terms “client device” and “content provider” as used herein may refer to software providing client and content providing functionality, to hardware on which the software executes, or to the entities operating the software and/or hardware, as is apparent from the context in which the terms are used.

The mobile device 135 may comprise a personal computer or other network-capable device such as a personal digital assistant (PDA), a mobile telephone, a pager, a television “set-top box,” and the like. The mobile device 135 may act as a client device 170 or as a content provider 130, depending on whether it is receiving content to be viewed by a user, or generating gaming content to be stored or streamed by the video hosting service 105. The mobile device 135 is described further below with respect to FIG. 2.

The network 140 is typically the Internet, but may be any network, including but not limited to a LAN, a MAN, a WAN, a mobile wired or wireless network, a cloud computing network, a private network, or a virtual private network.

Asynchronous Architecture

FIG. 2 illustrates one embodiment of a mobile device 135. In various embodiments, media processing (audio/video decoding/playback or encoding/muxing) on a mobile 135 device uses a pipeline of components. In the embodiment shown in FIG. 2, the mobile device 135 includes one or more media content generators 201, an application launcher 230, a user interface module 240, an audio capture module 202, an audio encoder 220, a video capture module 206, a video encoder 218, a frame rate conversion (FRC) module 214, an audio/video (AN) multiplexer 210, and local storage 222. In other embodiments, the mobile device 135 contains different and/or additional elements. In addition, the functions may be distributed among the elements in a different manner than described. For example, in some embodiments, the functionality for launching a screencast user interface is built into one or more of the media content generators 201 rather than being provided by an application launcher 230.

In one embodiment, the various components of the mobile device 135 communicate by passing data buffers between them. In another embodiment, communication between components is actively managed by a process that periodically polls each component for empty/full status and drains/fills/transfers buffers accordingly. However, this can incur a significant performance penalty, as maintaining the flow for audio can involve using a high polling rate, which in turn consumes processing resources that could otherwise be dedicated to the applications running on the mobile device 135. When the goal of the media pipeline is to record the behavior of another executing target application (e.g., a game), the added overhead can detract from the performance of the target application.

In some embodiments, an asynchronous architecture is used to manage the data flow so that the overhead is reduced on mobile device 135. As audio/video codecs consume or generate data, the mobile device 135 generates a control interrupt. The relevant component of the mobile device 135 can then quickly take action and either request input buffers to be filled by the generating component (e.g., audio capture module 202) or pass them to a consumption component (e.g., the A/V multiplexer 210), each of which executes asynchronously as well. In one embodiment, no software is involved during the normal flow of data, i.e., only errors generate an interrupt to software.

The media content generators 201 create media content of one or more types. In various embodiments, the media content generators include game applications executing on the mobile device 135, other applications executing on the device, the operating system of the device, one or more cameras of the device, and one or more microphones of the device. In one embodiment, the media content includes video layers and audio layers. The mobile device 135 combines the video layers into a single output layer and presents them on a screen or other display. For example, the video layers might include the graphics of a game, a view of the user taken with a front-facing camera, and a set of notification icons generated by the operating system. In this scenario, the mobile device 135 might display the game graphics full-screen, overlay the view of the user in the top-right corner of the screen, and either hide the notification icons or display them in a notification bar at the top of the screen. Similarly, the audio layers are mixed together and played through a speaker.

The application launcher 230 is used to launch other applications (e.g., media content generators 201) on the mobile device 135. In various embodiments, on launching an application, the application launcher 230 detects whether it is a media content generator 201 (e.g., a game) for which screencasting functionality is available. In one embodiment, a user can register particular applications or categories of applications to be auto recorded. When those applications are subsequently launched, the screencast recording system is activated automatically prior to starting the application and automatically stopped when the application process terminates (or the application launcher 230 otherwise regains control). This does not require any changes to the applications to screencast and can thus be applied to existing applications. Alternatively, the functionality for controlling a screencasting session can be built into the application for which screencasting is desired.

In other embodiments, a standalone system can be used in which the user registers applications or categories of applications to be recorded. In one such embodiment, a screencasting daemon runs in the background on the mobile device 135. On detecting the launch of such an application, the daemon activates the screencasting service. In another embodiment, application launches are detected through standard system notifications.

In another embodiment, applications issue system notifications at certain points in the application's lifetime (e.g. launch, termination, etc.), and, if present on the device, the screencasting service reacts by automatically initiating and terminating a screencast session. Other notifications can also be used to indicate that certain events should be demarcated within the screencast itself (e.g. achieving a new high score in a game app). This scheme involves application modification (e.g., modifying a game to issue a pseudo-system notification when a high score is achieved).

The user interface module 240 provide an interface (e.g., on a display of the mobile device 135) for the user to control the screencasting functionality. In various embodiments, the user interface is provided as an overlay atop the captured screencast visual data (e.g., as screencast control panel in one corner of the display and/or a self-cam of the user in another corner). Compositing these overlays onto the screencast requires additional processing and resources that can be costly for mobile devices where such resources can be limited (relative to desktop computers). In one embodiment, the overlay is generated and then inserted into the normal view system of the underlying OS. In this way, the system compositor can be used to blend the overlay with the rest of the system UI in the normal fashion, which is typically accelerated with a hardware compositor or via a GPU. This eliminates the ability to perform some post processing enhancements typically done in other screencasts (e.g., displaying the overlay but not recording it), but the performance savings can outweigh this loss in some configurations.

In various embodiments, a camera on the mobile device 135 (e.g., a front facing camera) is used to insert a view of the user into the screencast video (e.g., in an inset box in one corner of the display). In one embodiment, the user interface module 240 provides controls to change the camera view (e.g. to a rear-facing camera) or to swap the camera preview for a static image (e.g. the user's avatar, an emoji sticker, etc.). Alternatively or additionally, these controls can be embedded within the camera preview via hot zones or gestures, such as swipe, drag, or double tap. In some embodiments, the user interface module 240 provides controls for applying filters to the preview video (e.g., black and white, sepia, pincushion, etc.), mixing audio sound effects into the audio track (e.g., laugh track, applause, etc.), and temporarily drawing atop the entire screen (e.g., to highlight a section of screen content).

The audio capture module 202 selectively captures audio layers for screencasting. In one embodiment, the audio capture module 202 provides a user interface with which a user can select the audio layers to include in the media content for screencasting. For example, a user might elect to include the audio generated by a particular game and the mobile device's microphone, but not system notifications or the output of a music player. Thus, the user can listen to music and be notified of events (e.g., incoming calls and text messages) without those elements of the local audio being recorded as part of the screencast media content. In another embodiment, the audio layers that are captured for screencasting are pre-determined.

The audio encoder 220 uses an audio codec to encode the selected audio layers. In one embodiment, the audio encoder 220 selects and configures the codec at the start of a live streaming session based on the available hardware at the mobile device 135. In another embodiment, the audio encoder 220 dynamically adjusts encoding parameters based on resource availability. For example, the bit rate can be reduced when network bandwidth is scarce. This dynamic adjustment can be performed automatically or in response to user input.

The video capture module 206 selectively captures video layers for screencasting. In one embodiment, the video capture module 206 provides a user interface with which a user can select the video layers to include in the media content for screencasting. For example, a user might elect to include the video generated by a particular game and the mobile device's front-facing camera, but not system notifications. Thus, the user can be notified of events (e.g., incoming calls and text messages) without those elements of the local display being recorded as part of the screencast media content. In another embodiment, the video layers that are captured for screencasting are pre-determined.

The video encoder 218 uses a video codec to encode the selected video layers. In one embodiment, the video encoder 218 selects and configures the codec at the start of a live streaming session based on the available hardware at the mobile device 135. In another embodiment, the video encoder 218 dynamically adjusts encoding parameters based on resource availability. For example, the quality or frame rate can be reduced when network bandwidth is scarce. This dynamic adjustment can be performed automatically or in response to user input.

In one embodiment, when screencasting, raw video frames are generated by the media content generator 201 at the refresh rate of the display, and these frames are fed directly into a video encoder 218. In other embodiments, the target frame rate for the video does not match the display refresh rate. Therefore, the mobile device 135 includes a FRC module 214 that sits between the media content generators 201 and the video encoder 218. In one such embodiment, the FRC module 214 maintains a small buffer of frames (e.g., one frame), and then pushes frames out in a “leaky bucket” style to the video encoder 218, which acts as the consumer. Buffer overflow does not occur, as the FRC module 214 is responsible for applying a policy to select the most meaningful frame at any given time for output, dropping or duplicating frames as needed.

In various embodiments, the A/V multiplexer 210 combines the encoded video and audio data in to a single media container object. Examples of media container objects include AVI, MP4, MOV, and WebM. In other embodiments, the video and audio components are kept separate and the A/V multiplexer 210 generates metadata indicating how the two should be synchronized during playback.

In one embodiment, the local storage 222 is one or more non-transitory computer-readable media that store the various codecs available to the video encoder 218 and audio encoder 220 as well as any media content that the user elects to save.

In various embodiments, media content is streamed live from a mobile device 135 via a transmission control protocol (TCP) connection to access a remote server (e.g., video hosting service 105) through a firewall. TCP is known for its slow flow control mechanisms that do not drop data, both of which can be detrimental to live video streaming. When network quality of service deteriorates, the sender would like to reduce its transmission rate, drop video data, etc. Unless the remote server utilizes an out-of-band flow control mechanism, such as real-time transport control protocol (RTCP), the client/sender cannot react to changing network conditions.

To address this, various embodiments use a scheme whereby the mobile device 135 can detect network conditions locally with no feedback from the remote host and adjust its transmission accordingly. According to the scheme, each chunk of encoded media content data is queued to a separate network transmission processor. The depth of this queue relative to chunk data size is then monitored. An increasing queue depth indicates network congestion, and the encoding process can be adjusted accordingly.

In an alternate scheme, as encoded media content data is generated, a locally created timestamp is assigned to chunks of data (e.g., network abstraction layer (NAL) units as they exit the video encoder 218). These data chunks are transmitted over the streaming TCP connection, and the start/end time of transmission is noted. The latency between data generation and transmission start and the outgoing transmission rate are monitored. In some embodiments, when monitoring such values, common mathematical techniques such as exponential moving averages and hysteresis are employed to smooth out individual changes and reaction thresholds accordingly. Increases in these values indicate network congestion or other network issues, and the encoding process can be adjusted accordingly, (e.g., by dropping data, reducing the encoder bitrate, etc.). Additionally, to address the issue of long transmission delays, the time between subsequent data chunks can be determined by tracking the time at which frames enter the encoder or via a priori knowledge of the frame rate, and when transmission time for a chunk exceeds its allotted time or the expected transmission time based on expected bandwidth, a low network capacity situation can be detected.

In one embodiment, a transmission window scheme can be employed without relying on remote acknowledgements. Instead, the successful transmission of a chunk of data includes an implicit acknowledgement, and transmission credits are consumed periodically while a transmission request is active and returned when transmission completes. If the number of credits drops too low, network congestion is indicated. The number of credits to return to the pool of available credits when a chunk is transmitted successfully is determined by the frame rate.

FIG. 3 illustrates a conceptual buffer scheme for display sandboxing, according to one embodiment. A limitation of some existing display recording mechanisms for remote displays is that they can only capture the entire screen, which introduces a privacy issue for users, as unanticipated content may be captured. In some embodiments, this issue is addressed by duplicating the display content of a target application into a separate layer or a secondary virtual display, but this can impact latency and performance. In other embodiments, this functionality is migrated into the graphics framework where the display output for a particular application can be sandboxed.

In some embodiments, selected video layers 310 are passed to a pre-compositor 330 that composites them into a single output layer. This output layer is then passed to a video encoder 218 (for encoding into a stream for screencasting) and a compositor 340. The compositor 340 also receives the non-selected video layers 320 and composites them with the output layer produced by the pre-compositor to produce a local display layer. This local display layer is passed to the display 350 of the mobile device 135 for local presentation. Thus, the graphics framework of the mobile device 135 is extended to pre-composite the layers used by a particular application and route them to both a video encoder 218 and a downstream compositor 340, which prepares the local display. In one embodiment, video buffers support multiple consumers to avoid additional data copies being made. Note also that many applications particularly games, utilize a single layer, and as a result a fast path can be employed in which there is no pre-composite step, thereby freeing graphics hardware resources.

FIG. 4 illustrates operation of a video capture module 206, according to one embodiment. Screencast support can be delivered as a standalone service that other applications (or the system 100) can utilize to make local recordings or stream live. In various embodiments, the video capture module 206 collects a set of input layers 410 that have been selected to record and configures the graphics framework to composite those layers into a single output layer 430. The video capture module 206 provides the target output layer, which is typically the input layer of a video encoder 218 but could be any standard layer so that the application could apply additional effects to the composition, such as frame rate conversion (e.g., using the FRC module 214) or visual transforms. The video capture module 206 is responsible for periodically producing a result in the output layer 430. In one embodiment, when a target layer is not set, capture is suspended.

In one embodiment, if all layers are specified for capture, a virtual display for a presentation with auto mirroring is used to generate the composited result of the entire screen. In some implementations, this requires either privileged access to core functionality or an explicit grant of permission from the user.

FIG. 5 illustrates operation of a frame rate conversion module 214, according to one embodiment. In embodiments using a virtual display to source the capture frames, the underlying framework generates frames according to the update rate of the active applications. GL-based applications, such as games, update the display at 60 Hz, or as close as possible, depending on available resources. On the other hand, applications that are fairly static may generate frames only sporadically, e.g., at less than 1 Hz. One downside of a high frame rate scenario is that it can unnecessarily tax the video encoder 218 when the resulting video need only be at a lower frame rate (e.g., 30 Hz). For example, if a display system is not equipped to handle high frame rate video, the video will need to be down-converted. In contrast, in a low frame rate scenario, the receiving system (e.g., a YouTube live ingestion server) might require a GOP duration of approximately one to two seconds, and slow frame rates will exceed such requirements, resulting in video that is unplayable.

In various embodiments, the FRC module 214 accepts input frames 510 (e.g., the output layer 430 from the video capture module 206) at any rate and outputs frames 540 at a constant target rate (e.g., 10 Hz, 20 Hz, 30 Hz, 40 Hz, etc.). In one embodiment, the FRC module 214 utilizes a single frame-sized buffer 530 to hold the current output frame. In another embodiment, a buffer 530 that holds a greater number of frames (e.g., two frames) is employed for better performance at the cost of additional memory resources. As frames are input to the FRC module 214, they overwrite the frame buffer 530. A timing controller 550 directs the FRC module 214 to output the content of the frame buffer 530 at the constant target rate. This enables an incoming high frame rate to be down-converted to a lower frame rate by dropping frames, and steps up a lower frame rate by duplicating frames. In some embodiments, the FRC module 214 interpolates between frames using known up/down sampling algorithms.

FIG. 6 illustrates operation of a video encoder 218, in accordance with one embodiment. In the embodiment shown, the video encoder 218 receives frame data 610 (e.g., the output frame data 540 from the FRC module 214), selects a video codec based in part on available hardware support, and configures the video encoder parameters. The video codec provides an input layer 640, which the application can pass to the video capture module 206 or the FRC module 214 to be fed with data. Alternatively, the application can feed itself directly with data. In one embodiment, the application provides a reference to a muxer (e.g., A/V/multiplexer 210) where the outputted encoded video 650 should be directed.

In some embodiments, the video encoder 218 is responsible for periodically draining its output buffer and feeding the resulting data to the provided muxer handle. If it gets behind, the video encoder 218 drops frames. In one embodiment, the video encoder 218 notifies a feedback handler 660 that frames have been dropped. The feedback handler 660 can then take corrective action, such as reducing the quality of video captured by the video capture module 206, reducing the target frame rate for the FRC module 214, and the like. Thus, the video encoder 218 can respond to external resource constraint issues (e.g., network delays) without directly monitoring them.

In various embodiments, the feedback handler 660 monitors one or more feedback measures to determine whether the desired output frame rate (e.g., 30 Hz) is being achieved. In one embodiment, feedback handler 660 monitors an output buffer of the video encoder 218 and looks for buffer overflows (i.e., frames are being generated faster than they are output). In another embodiment, a credits system is used in which only a certain number of chunks of data can be transmitted at once. Credits are assigned to chunks of data to be transmitted and returned once transmission is successfully completed. If a new chunk of data is generated and there are insufficient credits to assign to it, this indicates that corrective action (e.g., reducing video quality or frame rate) is required. In still another embodiment, the feedback handler 660 monitors transmission time for data packets. If the time between generation and transmission gets above a threshold value (or is detected to be increasing), this indicates corrective action may be required.

FIG. 7 illustrates a conceptual buffer scheme for audio sandboxing, according to one embodiment. A limitation of some existing audio recording mechanisms for remote displays is that it can include audio streams from other applications or the operating system, which introduces a privacy issue for users, as unanticipated audio may be recorded. In one embodiment, the media framework is extended to sandbox the audio for recording by enabling applications to specify the audio tracks to be recorded, as well as the underlying support to create a mix of those tracks for duplication and delivery to the encoder. Typically, an application would specify its own audio tracks for inclusion, but it may also specify the microphone input for inclusion (e.g., using a sub-mix for the encoder that is not a pre-mix of the audio output).

In one embodiment, the audio inputs are conceptually separated into three groups: local audio input 710 (e.g., from a microphone), audio layers the application has requested be recorded 720 (e.g., its own audio), and other audio layers that are not to be recorded 730 (e.g., system notifications and phone calls). A user specifies which audio sources to record. For example, the user might want to stream audio from a game application and from the microphone, but not from the phone application, such that audio and visual notifications of an incoming call to the mobile device 135 will not be included in the broadcast.

Where more than one application-requested audio layer 720 is selected, these layers are sub-mixed 740. In one embodiment, the audio layers 720 are mixed using the raw output levels from the corresponding applications. In another embodiment, the audio capture module 202 applies automatic normalization to each layer to balance the levels. In yet another embodiment, the user can specify the level of each layer in the sub-mix 740. If the local audio 710 is selected to be included, the audio capture module 202 combines this with the sub-mix 740 to create a recording mix 750. As with the sub-mix 740, raw output levels, automatic normalization, or user specified levels can be used to determine the relative volume levels for the sub-mix and the local audio 710. The recording mix 750 is passed to the audio encoder 220 for encoding.

In one embodiment, the sub-mix 740 is separately combined with the audio layers that are not to be recorded 730 to create an audio output mix 760. As with the other mixing of audio layers, raw output levels, automatic normalization, or user specified levels can be used to determine the relative volume levels for the sub-mix 740 and the non-recorded layers 730. The audio output mix 760 is passed to one or more speakers 770 of the mobile device 135 for local presentation. Thus, the local audio output and the audio that is recorded can include different layers of the available audio.

FIG. 8 illustrates operation of an audio capture module 202, according to one embodiment. In the illustrated embodiment, the audio capture module 202 collects a set of input audio layers 810 (e.g., audio tracks that an application would like to record) and configures the audio framework to mix those tracks for recording. In some embodiments, the input audio layers 810 includes the microphone input.

In various embodiments, the audio capture module 202 provides compensation buffers 820 for storing the mixed audio data. In one embodiment, the audio capture module 202 also provides an output buffer 840 in response to a request from the audio encoder 220. In other embodiments, the audio capture module 202 also performs audio processing. The audio capture module 202 periodically triggers the mixer (e.g., to generate a recording mix 750) and stores the result in the output buffer 840. If at any point no output buffer is provided, capture is suspended.

In some embodiments, a data object is used to represent the application audio tracks 720, and a separate thread is used to poll the audio hardware and feed the output buffer 840. In one such embodiment, the data object is also used to read and mix sample data from the microphone 710. However, this approach may consume valuable resources, and the poll-based nature of the scheme can have the side effect of some data being lost, as the poller is detached from the audio encoder pipeline. In another embodiment, the microphone 710 is used to capture both device audio (as emitted from the speakers 770), as well as voice or other audio input from the user. This approach has the benefit of simplicity and low cost but lacks the flexibility of decoupling capture of system audio from the external audio (e.g., headphones with an external microphone cannot be used). This approach can also result in lower quality system audio capture. However, if a free running process is used to continuously read sample data from the microphone source and feed it to the audio encoder 220, on-demand capture from the audio encoder 220 is less likely to fall behind.

In various embodiments, these potential shortcomings are addressed through employment of a set of additional internal compensation buffers 820 to hold captured data that becomes available before new output buffers 840 are ready. Thus, fluctuations in system scheduling delays can be compensated for in most circumstances. However, in the event of excessive latency where other higher priority tasks are executing, some data may still be dropped.

In various embodiments, each output audio sample buffer 840 is tagged with a presentation timestamp for the encoder 218. To reduce the impact of scheduling delays, the timestamps are calculated based on the audio sample rate and number of samples delivered. This can result in high quality playback, but the playback can drift from the corresponding video frames over time. Thus, a synchronization comparison process 830 monitors the difference from real time using an exponential moving average to smooth out temporary scheduling anomalies. When the deviation becomes too high, the presentation timestamps are corrected to bring them closer to real time. In one such embodiment, this update is made as a single, abrupt change. In another embodiment, the update is made by a small set of changes over a longer interval. In a further embodiment, whether a single abrupt change or a series of gradual changes are used is determined based on the magnitude of the deviation relative to tolerances of the human ear. For example, a simple skip-ahead approach with small deviation threshold can be employed, so that the resulting audio artifact is not objectionable to the average listener.

FIG. 9 illustrates operation of an audio encoder 220, according to one embodiment. In the embodiment shown, the audio encoder 220 receives audio data 910 (e.g., the output buffer 840 from the audio capture module 202), selects an audio codec based in part on available hardware support, and configures the audio encoder parameters. The audio codec provides an input buffer 940 (e.g., from a queue of such buffers), which the application can pass to the audio capture module 202 or feed directly with data itself The application provides a reference to a muxer (e.g., AN multiplexer 210) where the outputted encoded audio 950 should be directed. In one embodiment, the audio encoder 220 provides an interface for adjusting the encoding parameters dynamically, which can be used to alter the quality and resource requirements according to resource constraints. For example, the bit rate can be reduced when network bandwidth is scarce.

In some embodiments, the audio encoder 220 periodically drains its output buffer and feeds the resulting data to the provided muxer handle. If it gets behind, the audio encoder 220 fills in empty data (silence). In one embodiment, the audio encoder 220 notifies a feedback handler 960 that silence has been inserted. The feedback handler 660 can then take corrective action, such as reducing the encoder bit rate. Thus, the audio encoder 220 can respond to external resource constraint issues (e.g., network delays) without directly monitoring them.

In various embodiments, the feedback handler 960 monitors one or more feedback measures to determine whether the desired output rate is being achieved. Possible feedback measures include buffer overflows, a credits system, and transmission times for data packets, as described above with references to FIG. 6. If the feedback indicates that the stream is not achieving the desired output rate, the audio encoder 220 reduces the quality of the audio to compensate (e.g., by reducing encoder bit rate).

FIG. 10 illustrates operation of an A/V multiplexer 210, according to one embodiment. The A/V multiplexer 210 receives encoded video data 1010 (e.g., an encoded video stream 650 produced by the video encoder 218) and encoded audio data 1020 (e.g., an encoded audio stream 950 produced by the audio encoder 220). The A/V multiplexer 210 stores the received data in an input buffer 1030 and multiplexes it to produce multiplexed media content 1040. In one embodiment, the multiplexed media content 1040 is packaged in a single container format (e.g., AVI, MP4, or MOV, WebM). The multiplexed media content 1040 can be directed to a stream transmission component 1050 for live streaming, directed to local storage 222 to be saved (e.g., for later uploading), or both.

In one embodiment, where the multiplexed media content 1040 is being directed to local storage 222 (e.g., in MP4 format), the process is halted when the local storage reaches full capacity. Additionally, the available capacity can be periodically provided to the application, which can then take action in advance of completely consuming local storage.

In embodiments where the multiplexed media content 1040 in streamed live (e.g., broadcasting the video via video hosting service 105, substantially in real time), the stream transmission component 1050 handles call setup, manages a network connection to the video hosting service ingestion servers, and addresses any feedback and synchronization issues associated with the channel. Network quality feedback is provided to the application so that it can adjust the screencast recording configuration in response. An example of a container format suitable for live streaming is the RTMP format with Advanced Video Coding (AVC) video and Advanced Audio Coding (AAC) audio. One of skill in the art will recognize that other container formats may be used.

The above components can be combined in a flexible configuration that enables the application to intercept the pipeline at various points and perform its own processing on the data. However, some applications will simply want to utilize standard configurations and standard feedback handlers. Consequently, default policy modules for recording to a local file and live streaming are included in various embodiments. These modules connect the components so that the application merely requests a file or stream pipeline, and they optionally handle adjustments between the quality levels. For example, policy modules can be used to configure the screencast pipeline whereby videos may be in any of a variety of video file formats and stream formats, and the pipeline configurations may include audio or not, have single or multiple video tracks, etc.

FIG. 11 illustrates the integration of the screencast system described above into a complete application for deployment, according to one embodiment. In the embodiment shown, the screencast service includes a service to host the API entry points from the application. Interface requests are dispatched to a capture controller 1100 that maintains a state machine for the capture and recording/streaming of the screen contents and microphone inputs. The capture controller 1100 executes in its own process and address space in order to isolate its effects from the host application and the target applications to capture. The capture controller 1100 instantiates the necessary screencast components outlined above and connects their various inputs and outputs to establish the full capture pipeline. It then manages the control plane between the components to ensure the pipeline operates correctly, that any error states are propagated back to the host application, and that the pipeline is properly dismantled upon request or in the event of fatal error conditions.

In one embodiment, the video input is driven asynchronously by a virtual display established to mirror the screen contents. As frames are generated, they are delivered to the FRC module 214, which drops or duplicates frames using a single GL-based frame buffer with hardware acceleration when present. The FRC module 214 releases frames to the video encoder 218 at a target 30 Hz. The video encoder 218 operates in an asynchronous fashion, delivering empty buffers to the FRC module 214 as they become available. Thus, it is possible for the video encoder 218 to get behind the FRC module 214 and not have buffers available when needed. However, in many implementations, this does not occur in practice, so the optimization of omitting further buffering in the FRC module 214 can be employed to conserve resources.

In various embodiments, the audio input is continuously sourced at the line rate of the microphone input 710 and fed to the audio encoder 220 as buffers become available. While it is possible to read the audio input 710 on demand as input buffers become available from the audio encoder 220, where a high sample rate is used (e.g., 44.1 KHz), the buffers may be delayed enough that the audio input does not keep up with the line rate. Therefore, in one embodiment, a separate audio process running at high priority is used to continuously read from the audio input 710 and ensure that samples are captured at the line rate. This may require additional buffering within the audio capture module 202 to hold sample data when input buffers from the audio encoder are delayed. When an encoder buffer becomes available, data from the oldest rate compensation buffers 820 are first copied to the encoder input buffers 940. If all the compensation buffers 820 are empty, audio data is read directly into the encoder input buffers 940. If all the rate compensation buffers 820 are full when the next samples are due to be read from the audio source, the oldest buffer is discarded in favor of the latest data, resulting in a gap in the audio stream. The size and quantity of rate compensation buffers 820 can be chosen based on empirical studies so as to minimize such dropouts. Finally, computed timestamps based on the sample rate and quantity read can be used to ensure smooth audio playback.

In various embodiments, the A/V multiplexer 210 executes in a separate thread for performance isolation, and it is driven via an event model from the encoders. As audio or video output buffers become available, the A/V multiplexer 210 is triggered, which then multiplexes the two streams into a unified container format (e.g., MP4 for recording to a file, and RTMP for live streaming). Executing in its own thread also enables the A/V multiplexer 210 to perform such tasks in a synchronous fashion, thereby simplifying its control logic without impacting the user experience. In one embodiment, a muxer factory is used to select an appropriate A/V multiplexer 210 based on the schema in a URI pattern used to name the target. Support for other schemas and container formats can thus be added in a straightforward manner. Muxers typically adhere to an interface that provides feedback to the controlling system (e.g., the capture controller 1100). For example, the file muxer monitors available storage and warns as it runs low, and the stream muxer monitors network load and warns when an appropriate data rate cannot be maintained.

In various embodiments, the screencasting functionality provided by the capture controller 1100 can be accessed by a first party screencasting application (e.g., 1P App 1110) using a developer interface, a third party screencasting application (e.g., 3P App 1120) via a client interface exposed through a software development kit (SDK) over standard interprocess communication, or remote procedure call mechanisms provided by the operating system. Alternatively, the screencasting functionality can be accessed directly from a game application (e.g., Gaming App 1130) by integrating the capture controller library/SDK directly into the application.

In various embodiments, the screencast capture and recording/streaming host application 1140 provides user experience (UX) integration, although common UI components could also reside within the screencast service so as to enable a consistent experience across applications. UI components utilized by one embodiment of a sample host application include: green room launch dialogs, a control panel, a status bar, and a chat window. The green room launch dialogs are a series of screens that explain the feature to the user and provide a means for the user to configure a screencast session, specifying the type and quality of screencast, the application to capture, and providing the opportunity to notify the audience via social media. The control panel provides controls for managing a screencast session once it is established. The status bar provides information about the current session and the chat window enables the user to discuss the session with those viewing it while live streaming.

In one embodiment, once a screencast session is configured, a host service manages the UI state in concert with the capture controller state. The host service directs the remote screencast service to initiate and stop screencasting, and ensures that feedback from the screencast service is reflected in a user-visible fashion. This includes a health monitor, which reports the status of a recording or live stream in an on-screen status bar that floats above other UI components. Additionally, a chat manager component monitors chat messages for live streams and presents them in a floating chat window as they arrive. The primary UI component, though, is the control panel, which the user employs to manage the screencast. The control panel includes a self-view from either the front facing camera or the user's avatar. The control panel is also a floating window that sits atop all other UI components. In this way, the camera view can be captured directly via the screencast capture, rather than requiring recording a video from the camera and overlaying it atop the captured video frames. The control panel includes a set of control buttons to enable/disable audio capture, the camera view, and the chat window. It also includes a button to start/stop the screencast session.

FIG. 12 is a high-level block diagram illustrating one embodiment of a computer 1200 for use in a stream capture system 100. Illustrated are at least one processor 1202 coupled to a chipset 1204. The chipset 1204 includes a memory controller hub 1220 and an input/output (I/O) controller hub 1222. A memory 1206 and a graphics adapter 1212 are coupled to the memory controller hub 1220, and a display device 1218 is coupled to the graphics adapter 1212. A storage device 1208, keyboard 1210, pointing device 1214, and network adapter 1216 are coupled to the I/O controller hub 1222. Other embodiments of the computer 1200 have different architectures. For example, the memory 1206 is directly coupled to the processor 1202 in some embodiments.

The storage device 1208 includes one or more non-transitory computer-readable storage media such as a hard drive, compact disk read-only memory (CD-ROM), DVD, or a solid-state memory device. The memory 1206 holds instructions and data used by the processor 1202. In one embodiment, program modules formed of executable computer program instructions are stored on the storage device 1208, loaded into the memory 1206, and executed by the processor 1202.

The pointing device 1214 is used in combination with the keyboard 1210 to input data into the computer system 1200. The graphics adapter 1212 displays images and other information on the display device 1218. In some embodiments, the display device 1218 includes a touch screen capability for receiving user input and selections. The network adapter 1216 couples the computer system 1200 to the network 1210. Some embodiments of the computer 1200 have different or additional components than those shown in FIG. 12. For example, the video hosting service 105 can be formed of multiple computers 1200 operating together to provide the functions described herein. As another example, the mobile device 135 can be a smartphone or tablet and include a touch-screen that provides on-screen keyboard 1210 and pointing device 1214 functionality.

FIGS. 13A-G illustrate embodiments of a user interface for launching a screencasting sessiOn. In the embodiment shown in FIG. 13A, a screencast session can be launched manually from a menu 1300 provided by another application (e.g., a game, a game management application, or a screencast management application). The menu 1300 includes four options: switch accounts 1302, settings 1304, screencast 1306, and help & feedback 1308.

The switch accounts option 1302 provides access to controls for changing the active user (not shown). By selecting the switch accounts option 1302, the active user can be changed to a different account (e.g., by providing a user name and password, etc.). On selecting the settings option 1304, the user is provided with controls (not shown) for configuring the application that provided the menu. Similarly, selecting the option for help & feedback 1308 provides access to a help system and controls for submitting feedback (not shown) relevant to the application providing the menu.

Selecting the screencasting option 1306 provides access to the screencasting application. In one embodiment, selection of the screencasting option 1306 causes the dialogue box shown in FIG. 13B to be displayed. In this embodiment, the dialogue box includes a pair of buttons to choose between recording 1310 (e.g., saving the screencast content to local storage 222) or streaming 1312 (e.g., transmitting the screencast to a video hosting service 105). The dialogue box includes another pair of buttons for selecting between a high definition format 1314 and a standard definition format 1315. In the example shown in FIG. 13B, the user has selected the record button 1310 and the high definition option 1314 (or they have been selected by the application as default options). In FIG. 13C, the user has selected the stream option 1312 instead (or it has been selected automatically as a default). Similarly, if the standard definition option 1315 is selected, this is indicated by the center of the radio button being filled (not shown). In other embodiments, the dialogue box includes an option to both record and stream simultaneously and/or additional format options (e.g., a super high definition format, a lower definition format, etc.).

The dialogue box shown in FIG. 13B and FIG. 13C also include a pair of buttons for cancelling creation of a screencast session 1316 and continuing to the next stage 1318. In one embodiment, if the user selects the “next” button 1318, the dialogue box shown in FIG. 13D is displayed. In this dialogue box, the user is presented with a list of applications for which screencasting is available 1320. The applications in the list 1320 can be sorted alphabetically, by popularity with all (or a subset) of users, by recency of the last screencast, by frequency with which the user opens them, by frequency of screencast, or using any other method. One such method is to include the two most recently screencast applications first, followed by other applications recognized as games (e.g., in alphabetical order), followed by other non-system applications (e.g., in alphabetical order), followed by any system applications installed on the device. In the embodiment shown in FIG. 13D, only four applications are initially shown and the user can select an “All apps” option 1321 to view some or all of the other applications for which screencasting is available. In other embodiments, different numbers of applications are presented in the initial list 1320.

If the user selects an application from the list 1320, the user interface proceeds to the next stage. In one embodiment, the next stage depends on whether the user previously selected record 1310 or stream 1312. If the user selected record 1310, the application is launched and the screencasting session begins. However, if the stream option 1312 was selected, the dialogue box shown in FIG. 13E is displayed to enable the user to set up the stream. The dialogue box directs the user to provide a title 1322 and description 1324 for the stream. In the embodiment shown in FIG. 13E, a suggested title 1322 and description 1324 are autofilled based on the application that the user selected.

In one embodiment, once the user has provided a title 1322 and description 1324 (and selected the next button 1318), the user is prompted to select one or more ways in which to share the stream. In the example shown in FIG. 13F, the user is presented a list of possible ways to share the stream 1328. As with the applications list 1320, the sharing options list 1328 shown in FIG. 13F has four options and an “other” option 1329 for accessing additional options, but any number of options may be included in the initial list. The list of sharing options 1328 can ordered by frequency of use by the user, frequency of use by the user, popularity with all (or a subset) of users, or the like. In one embodiment, the user can select as many options from the list 1328 as desired and then select “ok” 1326 to proceed to the next stage. Alternatively, the dialogue box allows only one option to be selected and proceeds automatically after the user makes a choice.

In one embodiment, after the user has selected one or more ways to share the stream, the dialogue box shown in FIG. 13G is displayed. This dialogue box includes a comment area 1330 for the user to provide a description of what is being shared and a preview area 1332 that includes a link to the stream and information about the hosting site. In the embodiment shown, the comment area 1330 is automatically filled based on the application the user selected to screencast, but the user can change or add to the automatically generated text. Once the user is ready to share the screencast stream, the user selects the “share” button 1334 and the provided information (including a link to the stream) is shared via the avenues the user selected from the sharing options list 1328.

FIGS. 14A-K illustrate embodiments of a user interface for operating a screencast sessiOn. In the embodiment shown in FIG. 14A, an application 1400 is running on a device (e.g., a mobile device 135). A screencast application is also running. The screencast application can be launched either automatically in response to detecting launch of the application 1400 or manually in response to user input (e.g., using the process illustrated in FIGS. 13A-G). The screencast application overlays a control panel 1402 over the application 1400. It also places a notification 1404 in a notification bar indicating that screencasting is active. In FIGS. 14A-K, the control panel 1402 appears in the bottom left hand corner of the screen. However, in other embodiments, it appears in other locations. Furthermore, in some embodiments, the user can move it around the screen (e.g., by long pressing on the control panel 1402 and dragging it to a desired location. In one such embodiment, the control panel 1402 is limited to appearing at the sides of the screen, and will “stick” to a point on the side of the screen nearest to where the user attempts to drag it.

In some embodiments, the control panel 1402 is rendered in a layer that is always above all other graphical layers and thus always visible. Thus, the user can launch different applications and record them, or even record multiple applications, switching between them during a single recording session, and maintain control of the screencast session. The control panel 1402 and notification 1404 also serve as a reminder to the user that the display is being recorded and/or streamed. In one embodiment, the layer that includes the control panel 1402 is not included in the set of layers that are recorded for screencasting.

In one embodiment (e.g., as shown in FIG. 14B), the control pane 1402 includes an information area 1410, a microphone button 1412, a camera button 1414, and a record button 1416. Referring back to FIG. 14A, when the screencast pane 1402 is first displayed, the information area 1410 includes a message instructing the user to tap the record button 1416 when ready to begin recording. The information area 1410 also includes a volume indicator and a time counter indicating the amount of video that has been recorded (in this case, currently none). The volume indicator assists the user in setting volume levels to avoid distortion of his or her voice if too loud and poor signal-to-noise ratio if too quiet. In embodiments, where the microphone is used to record the game audio (rather than obtaining it via audio sandboxing), this also helps the user ensure the game volume is loud enough to be picked up by the microphone. In some embodiments, the controls 1412, 1414, and 1416 disappear after a short time of non-use (e.g., five seconds) and reappear if the user taps on (or otherwise selects) the information area 1410.

FIGS. 14B and 14C illustrate operation of the microphone button 1412, according to one embodiment. In FIG. 14B, the microphone is enabled (indicated by the microphone icon within the microphone button 1412) and thus the screencast application is recording audio. Consequently, the volume indicator in the information area 1410 is showing audio being recorded at approximately 35% of maximum volume. In FIG. 14C, the user has tapped on (or otherwise selected) the microphone button 1412 to disable audio recording. Consequently, the icon on the microphone button 1412 has been replaced by one with a line through the microphone, and the volume indicator is not showing any audio being recorded.

FIGS. 14D and 14E illustrate operation of the camera button 1414, according to one embodiment. In FIG. 14D, the camera is enabled (indicated by a camera icon in the camera button 1414) and thus the screencast application is recording video (e.g., using a front-facing camera of a mobile device 135). In some embodiments, a preview of the video being recorded is displayed in the information area 1410 so the user can see what is being included in the screencast. In FIG. 14E, the user has tapped on (or otherwise selected) the camera button 1414 to disable video recording. Consequently, the icon on the camera button 1414 has been replaced by one with a line through the camera. In some embodiments, where the information area 1410 includes a preview of the video while the camera is enabled, the video preview is replaced by a static image when the camera is disabled (e.g., the user's avatar, the last frame recorded before the camera was disabled, etc.).

FIGS. 14F and 14G illustrate operation of the record button 1416, according to one embodiment. In the embodiment shown in FIG. 14F, the user has tapped on (or otherwise selected) the record button 1416 and the information area 1410 is displaying a countdown (e.g., in seconds) indicating how long it is until recording begins. As shown in FIG. 14F, the other controls disappear during the countdown. Alternatively, the controls may remain displayed (e.g., enabling the user to cancel the start of recording by selecting the record button 1416 again. In FIG. 14G, recording has begun, and the record button 1416 has changed to a stop icon indicating that the user can end recording by tapping (or otherwise selecting it). The information area 1410 includes a timer indicating how much material has been recorded. In one embodiment, the information area 1410 also includes an indicator that recording is currently underway, such as a pulsating change in color or intensity, a block of color or shading spinning around the outside of the information area, or the like.

FIGS. 14H and 14I illustrate a process for applying filters to the video recorded by a camera, according to one embodiment. In the embodiment shown in FIG. 14H, the information area 1410 is displaying the preview of the video being recorded by the camera, and a pair of chevron-shaped controls 1418 and 1420 overlay the video preview. By tapping on the left- pointing chevron 1418 and the right-pointing chevron 1420, the user can browse backwards and forwards through available filters to apply to the video, respectively. For example, in FIG. 14I, the user has applied an invert filter. Consequently, the preview of the video (and the recorded video) has the colors inverted. One of skill in the art will recognize other such filters that may be applied to the video.

FIGS. 14J and 14K illustrate two ways of ending a screencasting session, according to various embodiment. In the embodiment shown in FIG. 14J, the user is moving the screencast controls 1402 (e.g., by pressing and holding on the controls and then dragging them across the screen). When the user is moving the controls 1402, an area of the display 1430 is indicated as corresponding to an instruction to end the screencasting session. In FIG. 14J, this area 1430 is indicated by displaying an ‘X’ in an upper-central portion of the screen. In other embodiments, other indicators are used. If the user moves the controls 1402 into the indicated area 1430 (e.g., by dragging the controls to that area and then releasing his or her finger from the screen), then the screencasting session is ended.

FIG. 14K illustrates an alternative method for ending a screencasting session, according to one embodiment. In FIG. 14K, the user is viewing a notifications list 1440. In the list 1440, there are two notifications: one indicating that screencasting is active 1442 and another indicating that USB debugging is enabled 1444. If the user taps on (or otherwise selects) the screencasting notification 1442, the session is ended. In an alternative embodiment, after selecting the screencasting notification 1442, the user is prompted to confirm whether the screencasting session should be ended. In other embodiments, different or additional methods of ending a screencasting session are used. For example, in some embodiments, if the user stops recording by selecting the record button 1416 or exits the particular application that was being screencast, the session is automatically ended.

Some portions of above description describe the embodiments in terms of algorithmic processes or operations. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs comprising instructions for execution by a processor or equivalent electrical circuits, microcode, or the like. Furthermore, it has also proven convenient at times, to refer to these arrangements of functional operations as modules, without loss of generality. The described operations and their associated modules may be embodied in software, firmware, hardware, or any combinations thereof.

As used herein any reference to “one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.

Some embodiments may be described using the expression “coupled” and “connected” along with their derivatives. It should be understood that these terms are not intended as synonyms for each other. For example, some embodiments may be described using the term “connected” to indicate that two or more elements are in direct physical or electrical contact with each other. In another example, some embodiments may be described using the term “coupled” to indicate that two or more elements are in direct physical or electrical contact. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. The embodiments are not limited in this context.

As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present). In addition, use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the disclosure. This description should be read to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise.

Upon reading this disclosure, those of skill in the art will appreciate still additional alternative structural and functional designs for a system and process for providing capture, recording, and streaming of media content. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the described subject matter is not limited to the precise construction and components disclosed herein and that various modifications, changes and variations which will be apparent to those skilled in the art may be made in the arrangement, operation and details of the method and apparatus disclosed herein. The scope of the invention is to be limited only by the following claims. 

What is claimed is:
 1. A computer-implemented method for screencasting media content from a first device to a second device, the method comprising: responsive to determining that a first application has been launched, displaying a user interface (UI) comprising a screencast UI element at the first device; receiving, via user input using the screencast UI element of the user interface at the first device, an instruction to begin screencasting; determining, by the first device, a rate of screencasting to be supported by the first device; and responsive to the instruction, screencasting, at the determined rate, from the first device to the second device, media content including content created by the first application.
 2. The method of claim 1, wherein the first device is a mobile device and the second device is a mobile device or a server device.
 3. The method of claim 1, wherein the user interface displayed at the first device is a screencast control panel provided by a second application that is different from the first application.
 4. The method of claim 1, wherein the rate of screencasting is determined by a frame rate conversion (FRC) module hosted by the first device.
 5. The method of claim 4, further comprising: determining, by the FRC module, the rate of screencasting based on at least one of hardware of the first device or strength of network connection between the first device and the second device.
 6. The method of claim 5, further comprising: adjusting, by the FRC module, the rate of screencasting based on variation in output condition.
 7. The method of claim 6, wherein the adjusting the rate of screencasting comprises: maintaining a buffer of frames in the FRC module; and providing a number of frames in the buffer of frames to a video encoder.
 8. The method of claim 7, further comprising: applying, by the FRC module, a policy to determine the number of frames based on the variation in the output condition.
 9. The method of claim 8, wherein the policy is implemented by dropping or duplicating frames from the buffer of frames.
 10. A first device for screencasting media content created at the first device to be transmitted to a second device, the first device comprising: one or more processors configured to execute instructions that, when executed, cause the one or more processors to: responsive to determining that a first application has been launched, display a user interface comprising a screencast UI element at the first device; receive, via user input using the screencast UI element of the user interface at the first device, an instruction to begin screencasting; determine, by the first device, a rate of screencasting to be supported by the first device; and responsive to the instruction, screencast, at the determined rate, from the first device to the second device, media content including content created by the first application.
 11. The first device of claim 10, wherein the user interface displayed at the first device is a screencast control panel provided by a second application that is different from the first application.
 12. The first device of claim 10, wherein the first device includes a frame rate conversion (FRC) module that determines the rate of screencasting.
 13. The first device of claim 12, wherein the FRC module determines the rate of screencasting based on at least one of hardware of the first device or strength of network connection between the first device and the second device.
 14. The first device of claim 13, wherein the FRC module adjusts the rate of screencasting based on variation in output condition.
 15. The first device of claim 14, wherein the first device further comprises a video encoder, and the FRC module adjusts the rate of screencasting by: maintaining a buffer of frames in the FRC module; and providing a number of frames in the buffer of frames to a video encoder.
 16. The first device of claim 15, wherein the FRC module applies a policy to determine the number of frames based on the variation in the output condition.
 17. The first device of claim 16, wherein the policy is implemented by dropping or duplicating frames from the buffer of frames.
 18. A non-transitory computer-readable storage medium comprising instructions for screencasting media content created at a first device to be transmitted to a second device, the instructions, when executed by a processor, cause the processor to: responsive to determining that a first application has been launched, display a user interface comprising a screencast UI element at the first device; receive, via user input using the screencast UI element of the user interface at the first device, an instruction to begin screencasting; determine, by the first device, a rate of screencasting to be supported by the first device; and responsive to the instruction, screencast, at the determined rate, from the first device to the second device, media content including content created by the first application.
 19. The non-transitory computer-readable storage medium of claim 18, wherein the first device includes a frame rate conversion (FRC) module that determines the rate of screencasting based on at least one of hardware of the first device or strength of network connection between the first device and the second device.
 20. The non-transitory computer-readable storage medium of claim 19, wherein the FRC module adjusts the rate of screencasting based on variation in output condition. 